Windows Server 2003, Exchange Server 2003, Office 2007. The MAPI call 'OpenMsgStore' failed with the following error: The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000 This is the error message. ID: 6, Application Name: Microsoft Office Outlook, Application Version: 12.0.6514.5000, Microsoft Office Version: 12.0.6425.1000. This session was terminated unexpectedly. This is the outlook error message. When i try to open outlook screen becomes white and outlook closes with an error. I don't remember the whole text but it says exchange computer is closed or cannot be reached. As a result, this error repeats every 2-3 days. I restart exchange server services and outlook starts normally. It was fixed when i started information store or management service. When i restarted imap4 service, i remember that outlook haven't started. As a result, i can't find solution but it becomes annoying. How can i handle this? Edit : I found this link http://support.microsoft.com/default.aspx?scid=kb;en-us;328240 I looked at the registry but couldn't see an entry named disable mapi clients. And i don't want to restrict them, i want to give access to all my users.

Hi Rob, Its looking much resource utilizatipnin your mailbox sevrer, Did you check CPU and Memory spike at the time of problem occur. How much resource is being eating by store.exe, Also try to disable AV and any monitoring tool for some time anc check . Apart of this, I would suggest you to enable diagnostic logging on store level and analyze event log. How to Configure Diagnostics Logging:: http://technet.microsoft.com/en-us/library/aa996402(EXCHG.65).aspx http://support.microsoft.com/kb/329685 Anil

It seems your store.exe detection is right. There's no problem with the CPU but store.exe uses 625 mb of the memory, MSSql uses 1 Gb of it. Our server has 4 Gb of Ram and there's still 1.3 Gb of Ram available. Can it be a problem? I'll look at the links you've given. Thank you. Edit : Sorry to bother you but which exact services will i enable diagnostic logging on? There's Storage Limits category under public folder and mailbox. I couldn't find anything about analyze event log. If you give me names of the catalogs i'll be grateful.

I told my boss to add some memory to the server. Will this solve our problem, does anyone has an idea?

Consumption of store.exe is fine, I don't think this could be a problem as you have 1+ GB free in memory. I would suggest you to use Exchange Server 2003 Performance Troubleshooting Analyzer Tool (ExPTA) for trouble this. The Exchange Server Performance Troubleshooting Analyzer v 1.0 collects Exchange configuration data, several performance counters and some other information from an Exchange server http://www.msexchange.org/tutorials/Exchange-2003-Performance-Troubleshooting-Analyzer-Tool-v10-ExPTA.html For Enabling diagnostic logging for store you have to enable for MSExchangeIS.Anil

I downloaded Microsoft Troubleshooter and installed it. I'll let you know about the solution. Btw i've configured every category to maximum logging level under MSExchangeIS. I hope it won't cause memory problems. Thank you.

I started troubleshooter 2 times. First it said unusually high user activity is detected. High user activity - RPC per second per user is - 4,783. Second time it said moderate user RPC activity - 0,186. When i look at exmon i couldn't see a problem, maybe i'm not looking at the right place. We knew that there's a low disk space problem, less than 1 Gb. We're working on it. At last there's a network interface performance issue found. The average network interface\packets outbound error is greater than 0 packets. The measured value is 2 packets. I'm working on the problems. I think the disk space problem is the key.

I was wrong. I took a backup of exchange and log files are deleted. Now we have 30 gigabytes of free space but problem still continues. If i restart information store service everyday, there's no problem. But when i don't restart it for 1 day, problem occurs. We don't work on sundays and noone uses outlook as a result. But there's no change, on monday mornings we have a problem. As a result, disc space was not the main problem. Now i'll look for the other problems.